Skip to content

release: v0.1.1239 - #3755

Merged
kwakayama merged 1 commit into
mainfrom
release/v0.1.1239
Aug 16, 2026
Merged

release: v0.1.1239#3755
kwakayama merged 1 commit into
mainfrom
release/v0.1.1239

Conversation

@kwakayama

@kwakayama kwakayama commented Aug 16, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Contributor

Publishes the trigger target contract work to npm.

Why now

veryfront-code#3745 merged on 2026-08-15, after the v0.1.1238 release on 2026-08-14. git tag --contains 71ba942dc returns nothing and npm latest is still 0.1.1238, so the SDK change has never been published.

Proven against the published SDK from the template project veryfront/agentic-case-processing-salesforce:

✗ 1 schedules file failed to load:
✗   - schedules/triage-new-cases.ts: Schedule configuration.agentMessage is not supported.

The canonical authoring form is unusable until this ships. Source projects are stuck on the reserved-key spelling (input._schedule_target).

What ships

  • TriggerTarget carries agent conversation addressing; ScheduleDefinition gains agentMessage
  • declared-but-invalid conversation values fail loudly instead of deploying as none
  • a conflict means a disagreement — equal values in both locations are accepted, so one definition spans a platform upgrade
  • legacyScheduleTargetDiagnostic exported from veryfront/schedule so veryfront schedule run --input applies the same rules as schedule()

Release contents

Three files, per the release contract:

File Why
deno.json 0.1.1238 → 0.1.1239
src/utils/version-constant.ts version.test.ts asserts it matches deno.json
src/html/hydration-script-builder/hydration-runtime.generated.ts the prebundled runtime embeds the version string, so bumping the other two makes it stale

The third is the one that is easy to miss: its staleness check runs inside the typecheck task, so omitting it surfaces as a misleading type error. Regenerated with deno run -A scripts/build/prebundle-hydration-runtime.ts, not hand-edited.

Verification

deno test src/utils/version.test.ts   ok | 1 passed (21 steps)
deno task typecheck                   exit 0, no "is stale"

Bump confirmed above both origin/main (0.1.1238) and npm view veryfront version (0.1.1238) — not just claimed in the body.

Refs veryfront/veryfront-issue-inbox#517

Summary by CodeRabbit

  • Chores
    • Updated the application version to 0.1.1239.

@github-actions

github-actions Bot commented Aug 16, 2026

Copy link
Copy Markdown

📦 Client bundle boundary

Entrypoint Modules Source size Server leaks
src/index.client.ts 455 3071 KiB ⚠️ 39 known

A server module in a client graph aborts hydration in the browser. New leaks fail CI; known leaks are tracked in scripts/lint/client-bundle-baseline.json to burn down.

@coderabbitai

coderabbitai Bot commented Aug 16, 2026 •
edited
Loading

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6a6b9801-d58c-4b02-bb49-e37e037aaa65

📥 Commits

Reviewing files that changed from the base of the PR and between a583be3 and ab2a918.

⛔ Files ignored due to path filters (1)
  • src/html/hydration-script-builder/hydration-runtime.generated.ts is excluded by !**/*.generated.*
📒 Files selected for processing (2)
  • deno.json
  • src/utils/version-constant.ts

Included review availability: Your plan includes up to 3 reviews per rolling hour; 2 remain after this review.

📝 Walkthrough

Walkthrough

The release version was incremented from 0.1.1238 to 0.1.1239 in project metadata and the exported VERSION constant.

Changes

Release version metadata

Layer / File(s) Summary
Synchronize release version
deno.json, src/utils/version-constant.ts		 The project version and exported VERSION constant now use 0.1.1239.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to ab2a9

This release updates the package version consistently across the declared release files; no actionable merge-blocking risk remains after normal checks and review.

Possibly related PRs

Suggested reviewers: kojiwakayama

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the release version and matches the version updates in the pull request.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/v0.1.1239

Comment @coderabbitai help to get the list of available commands.

@kwakayama
kwakayama added this pull request to the merge queue Aug 16, 2026
Merged via the queue into main with commit e383111 Aug 16, 2026
36 checks passed
@kwakayama
kwakayama deleted the release/v0.1.1239 branch August 16, 2026 08:11
@kojiwakayama kojiwakayama mentioned this pull request Aug 17, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@kojiwakayama kojiwakayama Awaiting requested review from kojiwakayama kojiwakayama is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@kwakayama